1) Introduce new exception type XendInvalidDomain that maps to the high level
authoranthony@rhesis.austin.ibm.com <anthony@rhesis.austin.ibm.com>
Fri, 24 Mar 2006 13:31:12 +0000 (14:31 +0100)
committeranthony@rhesis.austin.ibm.com <anthony@rhesis.austin.ibm.com>
Fri, 24 Mar 2006 13:31:12 +0000 (14:31 +0100)
commit76e09e82387ec2eef675ae705348f655586b7bb3
treefbcb673585725ae3b56e703c502e6b016b83724c
parent3e0dfe69c98490d48b9706ec028756266a6af155
1) Introduce new exception type XendInvalidDomain that maps to the high level
   XEND_INVALID_DOMAIN faultType.
2) Fix exception logic in XMLRPCServer
3) Fix TCP server
4) Remove catching of ProtocolError in main.py.  ProtocolErrors only occur
   when there is an exception in the exception handling code which shouldn't
   ever happen.  I've reproduced the error cases described by Ewan with
   xend_domain_setTargetMemory and once I fixed the exception logic, I get a
   normal faultType of 1 as would be expected.

Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
tools/python/xen/xend/XendError.py
tools/python/xen/xend/server/XMLRPCServer.py
tools/python/xen/xm/main.py